templates
Here are 1,567 public repositories matching this topic...
-
Updated
Mar 28, 2020 - HTML
Template name: 101-event-grid, https://github.com/Azure/azure-quickstart-templates/blob/master/101-event-grid/azuredeploy.json
The parameter eventGridSubscriptionUrl's description ends with:
(RequestBin URLs are exempt from this requirement.)
This is no longer true, and deployments will fail, if the validation challenge is not answered, or the validation URL is not visited - even when
Since Python 3.7 dicts must preserve insertion order in all implementations (in Python 3.6 it was only an implementation detail in CPython). Thus I think it would make sense to state this in the loop section of the docs which currently states the following:
Note, however, that Python dicts are not ordered; so you might want to ei
Hello!
I was reading this post: SwiftGen/SwiftGen#228
Seems like one of the user was able to generate .imagestack from the Asset.assets. However when I tried it was only able to generate .imageset files.
Maybe I am missing something? My script is the same as the example one on Github for Assets.
Or is this not supported anymore?
Thanks!
This is not documented anywhere and happens silently, even when using debug
I've been using Sourcery to generate documentation automatically for GitHub wiki (i.e. generate markdown files based on types & annotations), as it's pretty user friendly on there (as in "easy to read") and also very easy to do in templates thanks to Sourcery's capability to generate files on the fly.
However, using annotations is not very "coder-friendly" though, as it gets hard to maintain be
Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example, .use and .define are provided by Base and implicitely added through Templates.
It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the @mixinand [`@mix
Refer to:
- commit-message-guidelines - robertpainsi
- Follow these git commit message guidelines - theserverside
- [Writing good commit messages](https://github.com/erlang/otp/wiki/writing-good-commit
Thanks for the easy-to-follow tutorial!
A few minor discrepancies between the tutorial and actual response for update (totally not urgent, these did not prevent any functionality -- just wanted to help keep things current):
On http://yeoman.io/codelab/scaffold-app.html
the following options in the CLI are missing from the tutorial page:
"Which Continuous Integration platform do you want? (Pre
-
Updated
May 14, 2020 - JavaScript
Document Translation
What is the PR? please refer to ant design pro.
Contributing:
- Fork ant-design-landing and
git clone. - Create a branch starting at
masterand name it astranslation-[xxx] npm install && npm start.- Find Markdown files and the
docs/*.mdanddocs/*/*.mduse d
-
Updated
Apr 3, 2020
Problem
https://github.com/blockstack/blockstack/blob/master/engineering/README.md
This document is far too large and contains manual steps (error-prone, must be remembered).
The process should be "build-in" to tools. As an example, the github-issue-tracker is not capable to model a more complex workflow.
If you favor "Sprints", use a tool where you can file the sprints.
If you f
I happened to see that sprig defines a function called hello while browsing the code.
While this is obviously an important function (added in the very first commit to the repo) it doesn't seem to
The link to Django version compatibility 1.7 in the README's Development status section is broken, it looks like this version is not supported anymore: https://docs.djangoproject.com/en/1.7/ref/templates/builtins/
I suggest to either include a reference of actually implemented filters in your project's documentation, or ensure support for Django 1.8 or higher so you can link to their document
Expected Behavior
When visiting the Shards UI demo page, using the left and right tooltip/popover examples places the info on the opposite of the expected side of the element.
Using data-placement="left" should place elements on the left. Similarly data-placement="right" should place elements on the right.
Current Behavior
Example screenshots:
