These are NOT product / license keys that are valid for Windows activation.
These keys only select the edition of Windows to install during setup, but they do not activate or license the installation.
These snippets provide a foundation for starting and stopping supervision trees at runtime using feature flags (e.g. Launch Darkly).
Some things to note when adapting these snippets:
- application.ex needs to be adapted into an existing application. The important part is that each child spec provided is compliant, and that there is a feature flag (
ld_key) specified. - As written, if a feature flag fails for some reason, it defaults to starting all children. There is room for adaptation here as needed.
- This implementation will still require a
FeatureFlagsmodule to be available that implementsis_on?/2. Adjust as needed to accomodate your own feature flag setup.
| // disable forced dark mode to prevent weird color changes | |
| // eslint-disable-next-line @typescript-eslint/no-var-requires | |
| const { createRunOncePlugin, withAndroidStyles, AndroidConfig } = require('expo/config-plugins') | |
| function setForceDarkModeToFalse(styles) { | |
| const newStyles = AndroidConfig.Styles.assignStylesValue(styles, { | |
| add: true, | |
| // ############# FOLLOW IF YOU'RE ON SDK 52 ############# | |
| // TODO: AndroidConfig.Styles.getAppThemeGroup() will be available in SDK 52 (or expo/config-plugins 9+), for now I just hardcoded AppTheme | |
| // parent: AndroidConfig.Styles.getAppThemeGroup(), |
For apps built before the image_processing gem became the default, the migration will involve two steps:
- Migrating to the image processing syntax while still using ImageMagick;
- Switching to Vips and updating the compression options;
Before changing from ImageMagick to Vips, it's better to first test the new syntax and ensure everything is still working.
variant(format: :jpg, strip: true, quality: 80)Repositório do projeto: https://github.com/fdaciuk/conduit-api
Especificação da API: https://gothinkster.github.io/realworld/docs/specs/backend-specs/introduction
Nx is a suite of powerful, extensible dev tools to help you architect, test, and build at any scale — integrating seamlessly with modern technologies and libraries while providing a robust CLI, caching, dependency management, and more.
It has first-class support for many frontend and backend technologies, so its documentation comes in multiple flavours.
Tiny wrapper component for React-Datepicker to stylistically fit with Chakra-UI 1.x.
<DatePicker selectedDate={myDate} onChange={(d) => console.log(d)} />
| import {useCallback, useRef, useEffect} from 'react' | |
| import {useField, useFormikContext} from 'formik' | |
| import update from 'immutability-helper' | |
| const useFieldArray = props => { | |
| const [field, meta] = useField(props) | |
| const fieldArray = useRef(field.value) | |
| const {setFieldValue} = useFormikContext() | |
| useEffect(() => { |
| import 'package:flutter/services.dart'; | |
| import 'package:intl/intl.dart'; | |
| class CurrencyPtBrInputFormatter extends TextInputFormatter { | |
| TextEditingValue formatEditUpdate(TextEditingValue oldValue, TextEditingValue newValue) { | |
| if(newValue.selection.baseOffset == 0){ | |
| return newValue; | |
| } |
Copyright © <year> <copyright holders>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell