mcnerdius / tailblazor-templates Goto Github PK

it won't be a 'runnable template' anymore but much simpler to maintain.

Regex test

The regex seems to work for every flavour except ECMAScript (which unfortunately VSCode uses), where in the example you can see that it no longer assigns groupings compared to the other flavours.

The regex is divided into two parts by the | character which means Alternate match. The part before | catches the Windows filepath and the latter part captures macOS/Linux. Using either of those parts on their own allows VSCode to correctly report the problem in the Problems pane with a link to the source code file, line and character - this can be tested by throwing some garbage characters into app.css

Short term solution could be to use the platform conditional in the template installation and insert the platform specific string, but it definitely isn't the right solution.

There is a second area to investigate which is how to reference the groups from the tasks.json file - but it seems to be a basic int reference.

tasks,json snippet so far:

{
      "label": "build & start tailwind jit/watch",
      "type": "shell",
      "command": "dotnet build -property TailwindBuild=false && npm run watch",
      "isBackground": true,
      "problemMatcher": {
        "owner": "external",
        "fileLocation": "absolute",
        "pattern": {
          "regexp": "([A-Z]:[^:]*):(\\d+):(\\d+):(.*)|(\\/[^:]*):(\\d+):(\\d+):(.*)",
          "file": 1,
          "line": 2,
          "column": 3,
          "message": 4
        },
        "background": {
          "activeOnStart": true,
          "beginsPattern": "Rebuilding\\.\\.\\.$",
          "endsPattern": "Done in \\d+ms\\.$"
        }
      },

This is work in progress, but just wanted to capture the actual regex in an issue in case others may have some ideas on how to make it work properly cross platform.

• Give #26 and tailblazor.dev issue 129 a common, more descriptive name.
• Update to TailwindCSS v 3.1
  • Other dependencies, too
• ... ?

Trying to follow along with the steps, and probably got something wrong along the way.

Running "npm run build" throws the following error:

> [email protected] build
> npx tailwindcss --config tailwind.config.js --postcss postcss.config.js -i site.css -o ./wwwroot/site.min.css

C:\Users\User\source\repos\CarpeDatumPortal\CarpeDatumPortal\Client\node_modules\postcss-import\lib\resolve-id.js:35
      throw new Error(
            ^

Error: Failed to find './obj/scopedcss/bundle/site.styles.css'
  in [
    C:\Users\User\source\repos\CarpeDatumPortal\CarpeDatumPortal\Client
  ]
    at C:\Users\User\source\repos\CarpeDatumPortal\CarpeDatumPortal\Client\node_modules\postcss-import\lib\resolve-id.js:35:13
    at async LazyResult.runAsync (C:\Users\User\source\repos\CarpeDatumPortal\CarpeDatumPortal\Client\node_modules\tailwindcss\peers\index.js:5153:15)

Node.js v17.3.0

Pointers appreciated :)

and get to the bottom of #5 :D

They "just worked" ... with a couple caveats so i didn't want to include them in the nuget package.

• Add back to repo but exclude from templates until they've been ironed out.
• Add back to templates with either an opt-in or opt-out for the .vscode folder. Reference
• Add opt in/out of watch.ps1 scripts while i'm at it.

• Ensure settings.json are up to date: things like explorer.fileNesting, terminal.integrated.autoReplies, etc.
• Make sure tasks and watch scripts are up to date.
• ... ?

• SP Server
• MP RCL
• MP Wasm
• MP Server
• SP Pages (lo priority)
• Hosted (lo priority)

I'm not sure whether this is the right place to create this, but creating this anyway.

Informative text in Index.razor gets mangled otherwise: "What is TailBlazor?" becomes "What is Project1?" sort of thing.

• Shared RCL
• Blazor-Wasm
• Blazor-Server
• RazorPages w/ Blazor ("Blazor Pages")

(MAUI TBD)

• Templates in sync
  • Correct page titles
  • gitignore
  • readme ?
  • ...
• Better template names, descriptions
• Better template icon. (Current one renders wonky in VS)
• Ensure prerelease flags set where needed
• ...

• Give McNerdius/TailBlazor#16 and tailblazor.dev issue 129 a new more descriptive name.
• Update to TailwindCSS v 3.1
  • Other dependencies, too
• ... ?

just make it a (complete) "what's in the box" & link to tailblazor.dev

ok so this repo is meant to be runnable dotnet templates, not visual studio templates, but if little noise is added to the "runnable" aspect to improve things, no problem. This won't happen.

• This is the approach i'd initially taken, but VS inverts the PNG in dark mode making it ugly. There's nothing in that schema about disabling inversion or an entry inverted icon.
• This is an old post about a hack to prevent color inversion when creating Visual Studio templates. No luck using the hack in a dotnet template.
• VS 2022 handles dotnet templates a bit differently from VS 2019 but i still haven't pinned down how to A) Provide a specific icon as an "Inverted" option or B) specify "don't invert icon.png for dark mode pls."

Find a solution or switch from somewhat arbitrary awesomeface to something that isn't ugly when inverted.

I was integrating a TailBlazor WASM template into my application. Noticed hot reload wasnt working when I launch it from a .Net Core hosted project that also contains the REST API. Only when I run the individual TailBlazor project does hot reload work.

seems like the only functional difference will be taking advantage of the new progress properties.

don't merge until november !

• Project GUIDs for example.
• Optional .vscode folder and watch.ps1 scripts.
  • Options added to CLI: how to expose in VS ?

prior repo was using GH Packages, shouldn't be too far off