77 Matching Annotations
  1. Mar 2021
    1. We added the X-Content-Type-Options: nosniff header to our raw URL responses way back in 2011 as a first step in combating hotlinking. This has the effect of forcing the browser to treat content in accordance with the Content-Type header. That means that when we set Content-Type: text/plain for raw views of files, the browser will refuse to treat that file as JavaScript or CSS.
    1. Software that is not currently being used gradually becomes unusable as the remainder of the application changes.
    2. Infrequently used portions of code, such as document filters or interfaces designed to be used by other programs, may contain bugs that go unnoticed. With changes in user requirements and other external factors, this code may be executed later, thereby exposing the bugs and making the software appear less functional.
  2. Feb 2021
    1. @adisos if reform-rails will not match, I suggest to use: https://github.com/orgsync/active_interaction I've switched to it after reform-rails as it was not fully detached from the activerecord, code is a bit hacky and complex to modify, and in overall reform not so flexible as active_interaction. It has multiple params as well: https://github.com/orgsync/active_interaction/blob/master/spec/active_interaction/modules/input_processor_spec.rb#L41

      I'm not sure what he meant by:

      fully detached from the activerecord I didn't think it was tied to ActiveRecord.

      But I definitely agree with:

      code is a bit hacky and complex to modify

  3. Jan 2021
    1. allow <slot> to be part of a slot
    2. I want to make some add-ons or wrappers on components e.g BigButton.svelte <script> import Button from './Button.svelte' </script> <Button fz="16" h="64" {...$$props}> <slot slot="prepend" name="prepend" /> <slot /> <slot slot="append" name="append" /> </Button>
    3. Related to #1824, can do <svelte:component this={Bar}> <slot></slot> <slot name="header" slot="header"></slot> </svelte:component> <script> import Bar from './Bar.svelte'; </script> as a forwarding workaround
    1. In 3.29.0 you can now use <slot slot='...'> to forward slots into a child component, without adding DOM elements.
    2. Would love to see passthrough slots to create superset components, for example Table and TableWithPagination (table slots for TableWithPagination could be passed through to Table).
    1. I’m not a dev either, so no Ubuntu fork, but I will perhaps be forced to look at Debian testing, without some advantages of Ubuntu - but now that Unity is gone (and I deeply regret it), gap would not be so huge anymore…
  4. Nov 2020
    1. Notably, LLVM and JVM are by far the most prominent targets in this scenario: they’re both open-source and well-documented targets that provide a ton of firepower, and there frankly aren’t a ton of other options.
    1. En ce sens, celui-ci ne peut légalement organiser une sélection pour l’accès à un enseignement optionne
    2. . En ce sens, celui-ci ne peut légalement organiser une sélection pour l’accès à un enseignement optionnel10. En revanche, le refus de procéder en cours d’année, à un changement de l’option initialement choisie par l’élève constitue une décision faisant grief et comme telle, susceptible d’un recours en annulation11. Plus précisément, le chef d’établissement doit procéder à un examen au cas par cas des demandes d’abandon d’option en cours d’année. Il ne peut opposer un refus systématique à toutes les demandes qui lui sont présentées, en faisant seulement valoir que ces changements provoqueraient des perturbations dans le fonctionnement du service12.

    Tags

    Annotators

    1. All standard UI events are forwarded on components, input events ("input" and "change") are forwarded on input components, and all MDC events are forwarded.
    2. You can add props to lower components and elements with things like input$maxlength="15".
    3. You can add actions to the components with use={[Action1, [Action2, action2Props], Action3]}.
  5. Oct 2020
    1. I debugged docker-compose and docker-py and figured out that you should either use environment variables or options in command. You should not mix these . If you even specify --tls in command then you will have to specify all the options as the TLSConfig object, as now TLSConfig object is created completely from the command options and operide the TFSConfig object created from the environment variable.
    1. export const validationSchema = {
        field: {
          account: [Validators.required.validator, iban.validator, ibanBlackList],
          name: [Validators.required.validator],
          integerAmount: [
      

      Able to update this schema on the fly, with:

        React.useEffect(() => {
          getDisabledCountryIBANCollection().then(countries => {
            const newValidationSchema = {
              ...validationSchema,
              field: {
                ...validationSchema.field,
                account: [
                  ...validationSchema.field.account,
                  {
                    validator: countryBlackList,
                    customArgs: {
                      countries,
                    },
                  },
                ],
              },
            };
      
            formValidation.updateValidationSchema(newValidationSchema);
          });
        }, []);
      
    1. We are looking to use React Final Form in our application at work. Evaluating our options and reading the documentation, we couldn't figure out how to address a specific use case.
  6. Sep 2020
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
    2. Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
    1. You'll have to create a new component that brings in the functionality of both. TooltipButton, TooltipLink, Link, and TooltipRoutedLink. We're starting to get a lot of components to handle a bit of added functionality.
    2. For the tooltip example, if you had a whole bunch of tooltips on different elements, it would be annoying to have different event listeners and "should it be shown" variables for each one.
    1. Perhaps at that point we're better off settling on a way to pass components through as parameters? <!-- App.html --> <Outer contents={Inner}/> <!-- Outer.html --> <div> <div>Something</div> <[contents] foo='bar'/> </div>
    2. I would hope for it to come with React-like behavior where I could pass in a string (like div or a) and have it show up as a normal div/a element when the child component used it.
    1. The lack of spread continues to be a big pain for me, adding lots of difficult-to-maintain cruft in my components. Having to maintain a list of all possible attributes that I might ever need to pass through a component is causing me a lot of friction in my most composable components.
    1. We should also allow passing unrecognised props to the rendered component. eg: tabindex might be required on some instances of a component, and not all. Why should developers have to add tabindex support to their components just that it may potentially be used

      Glad to hear this is solved now: $restProps

    2. You could do something like this instead while maintaining complete control of where different props go. <div class="wrapper> <div {...$$props} > ... </div> </div>
    1. Il faudrait procéder à une analyse très précise de la manière dont les options ont été implantées, suivies, favorisées dans les établissements concernés, examiner les raisons du peu de succès dans certains autres.
    1. Designing with constraints. Using inline styles, every value is a magic number. With utilities, you're choosing styles from a predefined design system, which makes it much easier to build visually consistent UIs.
  7. Aug 2020
    1. All of the components should allow passing MUI configuration properties to them so that they can be easily customized. In the case of RFF and MUI components with deeply nested structures of multiple subcomponents, you can pass the properties in with sepecial top level properties. This is very hard to document fully without making a mess, so please refer to the source code and demos for examples.
  8. May 2020
  9. Mar 2020
    1. Do you consider visitor interaction with the home page video an important engagement signal? If so, you would want interaction with the video to be included in the bounce rate calculation, so that sessions including only your home page with clicks on the video are not calculated as bounces. On the other hand, you might prefer a more strict calculation of bounce rate for your home page, in which you want to know the percentage of sessions including only your home page regardless of clicks on the video.
  10. Feb 2020
  11. Jan 2020
  12. Dec 2019
    1. More volatile underlying assets will translate to higher options premiums, because with volatility there is a greater probability that the options will end up in-the-money at expiration.

      That's interesting

    1. The option is European and can only be exercised at expiration.No dividends are paid out during the life of the option.Markets are efficient (i.e., market movements cannot be predicted).There are no transaction costs in buying the option.The risk-free rate and volatility of the underlying are known and constant.The returns on the underlying are normally distributed.

      Some of the assumptions underlying the Black-Scholes model. Do these limit its realism and predictive power?

  13. Nov 2019
    1. From the man pages The environment variables can be specified in lower case or upper case. The lower case version has precedence. http_proxy is an exception as it is only available in lower case. Using an environment variable to set the proxy has the same effect as using the --proxy option
  14. Sep 2019
  15. Nov 2018
  16. Jan 2018
    1. Default Value

      Please note that the values listed below are the default ones. An Option can represent a Boolean toggle flag (i.e. HeapDumpOnOutOfMemoryError, PrintConcurrentLocks). For such Options, '+' and '-' flags deal with Boolean toggling. In short:

      • '+' means Enable (or set to '1');
      • '-' means Disable (or set to '0').

      For example, in the table pertaining to Debugging Options, by default the -XX:-HeapDumpOnOutOfMemoryError is Disabled, because it has the - prepended to it. To actually Enable it, change that with +, yielding the variant -XX:+HeapDumpOnOutOfMemoryError.

  17. Sep 2016
    1. they are wrestling with how to get more Latinos to pick a race. In 2010, they tested different wording in questions and last year they held focus groups, with a report on the research scheduled to be released by this summer.

      Why do they want to force latinos to pick one race?? There are so many different microcultures and sub groups that latinos are included in, the Census would have to add so many more options.

  18. Feb 2014
    1. The other way to help these students would be to dramatically reduce the price or time required to get an education of acceptable quality (and for acceptable read “enabling the student to get a better job”, their commonest goal.) This is a worse option in every respect except one, which is that it may be possible.
  19. Jan 2014
    1. We distributed options every month, at a slight discount from the market price. We had no vesting period—the options could be cashed in immediately. Most tech companies have a four-year vesting schedule and try to use options as “golden handcuffs” to aid retention, but we never thought that made sense. If you see a better opportunity elsewhere, you should be allowed to take what you’ve earned and leave. If you no longer want to work with us, we don’t want to hold you hostage.