-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure rel="trunk-dist" will copy over directories #50
Labels
assets
Build pipelines for specific asset types
cli
Trunk CLI application
enhancement
New feature or request
good first issue
Good for newcomers
ready
Ready to be implemented
Milestone
Comments
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. closes #50
4 tasks
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 6, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
thedodd
added a commit
that referenced
this issue
Oct 8, 2020
All assets which are to be processed by trunk must now be declared as HTML `link` elements as such: `<link data-trunk rel="rust|sass|..." data-attr0 data-attr1/>`. The links may appear anywhere in the HTML and Trunk will process them and replace them or delete them based on the associated pipeline's output. If the link element does not have the `data-trunk` attribute, it will not be processed. The `--manifest-path` flag has been removed in favor of the new link style: `<link rel="rust" href="path/to/Cargo.toml"/>`. This is optional, and will default to the Cargo.toml of the source HTML's parent dir if not specified. Update README describing new asset pipeline declaration pattern. closes #50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
assets
Build pipelines for specific asset types
cli
Trunk CLI application
enhancement
New feature or request
good first issue
Good for newcomers
ready
Ready to be implemented
Right now, it expects the target to be a file. If it is a dir, we should recursively copy it.
The text was updated successfully, but these errors were encountered: