profile
viewpoint

brendon/acts_as_list 1627

An ActiveRecord plugin for managing lists.

dwilkie/carrierwave_direct 825

Process your uploads in the background by uploading directly to S3

fabn/activeadmin-globalize 31

Provides translation UI for ActiveAdmin and Globalize gems

fabn/capistrano-tags 6

Deploying SCM tags interactively or using ENV variables

fabn/acts_as_list 1

An ActiveRecord plugin for managing lists.

fabn/attachinary 1

Attachments handler for Rails that uses Cloudinary for storage.

fabn/cancancan 1

Continuation of CanCan, the authorization Gem for Ruby on Rails.

fabn/actioncable-examples 0

Action Cable Examples

fabn/active_admin 0

The administration framework for Ruby on Rails applications.

startedcoreui/coreui-free-react-admin-template

started time in 6 hours

issue openedcodeep/react-recaptcha-v3

Execute should return a promise or you should expose a refresh method

I'm having a problem with this scenario:

  • Load recaptcha
  • Load token <ReCaptcha ref={ref => recaptcha = ref} sitekey={siteKey} action='checkout' verifyCallback={filled}/>
  • Submit form with token, captcha validation is ok but some business data are wrong => form shows errors
  • User correct data and resubmit => captcha is reused

I'm having some trouble to get a new token with current interface. I'd like to use something

this.recaptcha.execute()
  .then(token => /* set new token on request */)
  .then(() => api.post(/* new data and new token*/))

or simply a new method that refresh the token with a promise something like

this.recaptcha.refresh() // verify is called again when promise is fulfilled
  .then(() => api.post(/* new data */)) // using the refreshed token

What do you think?

created time in 16 days

issue openedgetsentry/raven-ruby

Context should accept procs as values

I used other error tracking libraries and what I'm missing in sentry is the ability to provide context using a proc.

If I provide context in a before action as in the provided example

before_action -> do
  Raven.user_context = user_context
  Raven.tags_context = context_tags
end

when filter is run some values may not yet be available. If we're able to provide a proc (evaluated with current controller) we can add more useful data to context and get it when available.

Also I see that you're using thread locals (correctly) but you don't suggest to clear context after usage, this can leak context to other requests served by same thread. I'm using like this to avoid this issue.

  around_action :set_diagnostic_context

  # Used to record values in sentry
  def set_diagnostic_context(&action)
    Raven.user_context = user_context
    Raven.tags_context = context_tags
    action.call
  ensure
    Raven::Context.clear!
  end

is that correct?

created time in 23 days

create barnchfabn/datocms-Gatsby-Portfolio-Website-demo

branch : master

created branch time in a month

created repositoryfabn/datocms-Gatsby-Portfolio-Website-demo

created time in a month

startedtoretore/barby

started time in a month

startedimmuni-app/immuni-app-android

started time in a month

push eventfabn/pwa-react-typescript

Fabio Napoleoni

commit sha b44f4ff0727beeefccf34c40d5a188b804e34044

Add spa config for netlify

view details

push time in 2 months

push eventfabn/pwa-react-typescript

Fabio Napoleoni

commit sha 15a63c15dce094b847e3c10bf4ead0031cce0e39

Manifest customization

view details

push time in 2 months

push eventfabn/pwa-react-typescript

Fabio Napoleoni

commit sha cfa331c7255a3bc988f4e0173861e1037653f385

Ignore idea config

view details

Fabio Napoleoni

commit sha c38aff7b8fbad055369533b0f33afe9a26ca57ae

Add semantic ui to project

view details

Fabio Napoleoni

commit sha 0053466a210e97a0de34d35c6b9703129f55416a

Add semantic loader

view details

Fabio Napoleoni

commit sha b2a74e0b7e28bb186a85bfa48ba8dbb75855913c

Add layout with semantic react

view details

Fabio Napoleoni

commit sha 4279db24d6f1836b367bfa0c2dc9e5fd3af47f38

Customize home and about

view details

push time in 2 months

issue commentsimoneb/axios-hooks

Option to disable cache with makeUseAxios

@simoneb I tried it and it's working as expected. Thanks.

fabn

comment created time in 3 months

issue commentsimoneb/axios-hooks

Option to disable cache with makeUseAxios

I think is fine, as soon as you release it I'll test it.

Thanks.

fabn

comment created time in 3 months

issue openedSemantic-Org/Semantic-UI-React

Dropdown not showing all given options

Bug Report

Maybe I'm doing something wrong but I'm not able to understand what... I implemented an autocomplete component that uses algolia to get options and allow user to search in realtime.

By following that documentation I've used a Dropdown that receives hits as properties, shows them as option and refine search query while user types something.

The final result is pretty awesome but suddenly I realized that not all returned results are shown as dropdown options.

Steps

Here's a working demo of issue, you can try some searches to see that results are not the same, some values that trigger the "bug":

  • 00100
  • mil

But generally speaking if you search using dropdown and compare rendered results with other two panes you'll see that they are pretty inconsistent

Expected Result

Dropdown options should be same as list items in the middle

Actual Result

Not all options are rendered

Testcase

https://codesandbox.io/s/algolia-example-468ks

created time in 3 months

issue closedalgolia/react-instantsearch

Different results from SearchBox and connectAutoComplete (hits are filtered)

<!-- Thanks for participating in this project! We will try to answer as soon as possible 🙏 -->

Describe the bug 🐛

I'm switching to react and I'm thus removing old autocomplete widget.

I've built my react component by following this doc and almost everything is working, however there are missing hits comparing to same query for searchbox

By inspecting network requests done by two widgets I can see that request and responses from algolia are identical, so it must be something inside connectAutoComplete that filters out results.

Going into details I have city objects that has this shape in index:

{
  objectID: 1234,
  name: 'cityName',
  zip_code: '00123',
  fractions: ['fraction1', 'fraction2', ...]
  // other fields
}

And in my index settings I have as searchable attributes name, zip_code, fractions

When I search using search box for e.g. fraction1 or 00123 I get results, when I do same search using connected widget results are there (inspecting network requests), but hits for zip code and fractions are filtered out.

Is there any way to prevent this?

closed time in 3 months

fabn

issue commentalgolia/react-instantsearch

Different results from SearchBox and connectAutoComplete (hits are filtered)

Going to close this, I found that there's an issue in the inner component I'm using to render results, so it's not an algolia issue.

fabn

comment created time in 3 months

issue openedalgolia/react-instantsearch

Different results from SearchBox and connectAutoComplete (hits are filtered)

<!-- Thanks for participating in this project! We will try to answer as soon as possible 🙏 -->

Describe the bug 🐛

I'm switching to react and I'm thus removing old autocomplete widget.

I've built my react component by following this doc and almost everything is working, however there are missing hits comparing to same query for searchbox

By inspecting network requests done by two widgets I can see that request and responses from algolia are identical, so it must be something inside connectAutoComplete that filters out results.

Going into details I have city objects that has this shape in index:

{
  objectID: 1234,
  name: 'cityName',
  zip_code: '00123',
  fractions: ['fraction1', 'fraction2', ...]
  // other fields
}

And in my index settings I have as searchable attributes name, zip_code, fractions

When I search using search box for e.g. fraction1 or 00123 I get results, when I do same search using connected widget results are there (inspecting network requests), but hits for zip code and fractions are filtered out.

Is there any way to prevent this?

created time in 3 months

more