@afeefa/vue-app 0.0.311 → 0.0.312

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1 +1 @@
1
- 0.0.311
1
+ 0.0.312
@@ -0,0 +1,32 @@
1
+ # GitHub Copilot instructions for @afeefa/vue-app (summary)
2
+
3
+ Purpose: short, actionable notes so an AI agent or a new dev can be productive quickly in this package.
4
+
5
+ ## Big picture
6
+ - A small shared Vue 2 component & utility package used across multiple frontend projects. It exposes reusable UI components and helpers (see `docs/` for component docs/examples).
7
+ - This package is intended to be consumed by an application rather than run standalone — development usually happens by linking into a consuming app or by checking usage in the consuming repo.
8
+
9
+ ## Key workflows & commands
10
+ - No heavy build pipeline inside the repo itself; check the consuming app's build for how components are compiled.
11
+ - Check `package.json` for dependencies and ensure compatibility with consuming apps (Vue 2 v2.7.x and decorators used here).
12
+
13
+ ## Project-specific conventions
14
+ - Keep components and helpers small and opinionated — prefer explicit props and documented examples under `docs/components/`.
15
+ - Use `vue-class-component` / `vue-property-decorator` style for class-based components (see other Kollektiv frontends for usage examples).
16
+ - When changing shared behavior (auth models, date helpers, etc.) update all consuming apps or add migration notes in PR description.
17
+
18
+ ## Integration & external dependencies
19
+ - Uses Vue 2.7.x and decorator-style class components — upgrading Vue may require refactors in consuming apps.
20
+ - Common dependencies: `vuedraggable`, `moment`, `vue-shortkey` — ensure peer compatibility.
21
+
22
+ ## Common gotchas / shortcuts
23
+ - To check runtime behavior, link the package into a consuming project (e.g., `npm link` or `yarn link`) and run that app's dev server.
24
+ - When adjusting props or model shapes, update README/docs and the consuming apps to avoid runtime mismatches.
25
+
26
+ ## Where to look when asked to change code
27
+ - Component docs: `docs/components/`
28
+ - Package config: `package.json` (check Vue version and dependencies)
29
+ - Shared runtime helpers: `src/` (look for Auth-related helpers in other shared packages like `kollektiv-vue-app` for reference)
30
+
31
+ ---
32
+ If you'd like, I can add a small checklist for validating changes across consuming apps (linking, smoke tests, and example consuming apps to test with). ✅
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@afeefa/vue-app",
3
- "version": "0.0.311",
3
+ "version": "0.0.312",
4
4
  "description": "",
5
5
  "author": "Afeefa Kollektiv <kollektiv@afeefa.de>",
6
6
  "license": "MIT",
@@ -9,7 +9,7 @@
9
9
  class="mr-n2"
10
10
  @click="goToLastNamedRoute()"
11
11
  >
12
- <v-icon>
12
+ <v-icon size="24">
13
13
  $arrowLeftIcon
14
14
  </v-icon>
15
15
  </v-btn>